One suggestion, but this would require some work, is to have some external process that monitors the usage of each user. When they reach their cap, this process should then send a disconnect to RADIUS which disconnects the user. But before it does the disconnect it should switch the users class(room in this example) and this class will have the relevant attributes required to shape the user to the require speed. So when the user reconnects the new speeds are sent to pfSense for shaping.

It more depends on your through put. Personally I have never had a good experience with any low end budget router. I am running a ALIX board which is much more stable. I always found the budget routers to crash.

Apologize for the delay, was out of town. Yes you would, I am not sure though as I do not know anything about your BMU.

Well so how would I hand out my public IP's to my customers if the setup is like this: pfsense –--> BMU ----> routerboard ---->sectors                                               -                                               - to other towers with routerboards?

@dshafirov: The rest "make config && make package" is unknown territory.  And I'm reading the man pages and googling.  Any further hints would be appreciated. This is used only when compiling packages from ports.

We can't change the legal message from Intel. The license files are in the repo (See here) but something must have left them off the iso, probably somewhere in there it excludes the share portion of the build.

Ah, good suggestion but I have sorted it now. I'm not sure it would have worked though since I twice restarted to whole box (you can see the gaps in the RRD graph) and that just made it worse! It turns out I had left another computer on with multiple copies of the dashboard open that I had forgotten about. Interesting that the connection survived a reboot. However would you not expect to be able to see the system load using top -SH?  :- Is there some other tool I could use in future to diagnose something like this? Steve

Found the culpit. If you "Enable UPnP & NAT-PMP" it will broken miniupnpd. So miniupnpd cannot support it.  ::)

Yes, use search This question has been covered quite a lot

Thanks!  I've setup split dns and that's working so I'll probably just use that method, but shouldn't NAT redirection work since I don't have the "disable" option checked?

I only tried it with the latest version (2.0.1)  Although it will most likely work with 2.0.  I dont think it will work with anything before that.

Hmm ok, but this is not correct… This looks like it's just HTML/CSS/JAVA web design/code(s) and some other types of coding I might of overlooked, but changing resolutions is not suppose to shift things around. If the theme is suppose to be centered, then it's suppose to stay centered no matter the resolution... :) –>  By the way Ctrl + will only keep the page I'm on zoomed in and centered, as soon as I leave it and click to another section I'm back to where I started… :( THANKS

thus far the problem seems to have been solved we had 2 wan connections but one of them had been offline for a long time (issue's with the isp) the problem occured weekly, each time it had something todo with dhcp lease expiring and problem to renew them …. once we managed to get our secondary wan functioning again like it should, the problem went away.( a month now )

thanks :D i forgot to turn off and to disable joomla cache plugin. :)

You may want to try the Broadcom tuning options listed here: http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards Steve

It's working here fine, no issues checking for updates on amd64 and the widgets work fine.

marcelloc: I think you are not familiar with DSL Modem/Routers (Bell ones). Like I said, the pfSense WAN probably uses only the modem feature of the DSL modem/router to obtain another public IP. It has absolutely nothing to do with the other WAN even though it connects to a port labelled LAN on the DSL Modem/router. In fact, gateway is picked up automatically from ISP. Sometimes the public IPs are very different like 174.55.x.x and 94.22.x.x. I could be wrong on my assumption above with usage of the modem but that type of bridge mode is the only thing that comes to my mind. CMB: I think you are right. Let's see if they complain again. And yes, I don't like GoDaddy either (They hiked my certificate price double after a year of subscription knowing it's freaking time taking to install that SSL certificate again….). No firewall changes been done. Bouncing is a problem of GoDaddy indeed.